(WIP) - SDK 2223 DMA Consent Params Implementation #1345
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reference
SDK-2223 -- Design and implement key/values to represent consent param
Summary
+ (void) setDMAParamsForEEA:(BOOL) eeaRegion AdPersonalizationConsent:(BOOL) adPersonalizationConsent AdUserDataUsageConsent:(BOOL) adUserDataUsageConsent;
Motivation
Support new params added in Google Conversion API for DMA Compliance.
Type Of Change
Testing Instructions
-- SDK is sending value of
eeaRegion
, with every/v1/install
,/v1/open
,/v2/event
,v1/pageview
request.-- SDKis sending value of
adPersonalizationConsent
/adUserDataUsageConsent
with every/v1/install
,/v1/open
,/v2/event
,v1/pageview
request only if --
eeaRegion
istrue
OR-
eeaRegion
isfalse
andadPersonalizationConsent
/adUserDataUsageConsent
is also set tofalse
Ref : https://www.notion.so/brancheng/Google-DMA-Compliance-c19ed28d2ea74b2b9fa4d2d77f8cdcbe
cc @BranchMetrics/saas-sdk-devs for visibility.